Hi @Project516 , try to update this script to understand this PR as a whole:

Rationale for this change

Explain the reasons to change the repository

What changes are included in this PR?

Explain what changes do this PR

Are these changes tested?

Explain if the PR was tested and explain details

Are there any user-facing changes?

Explain if the PR will impact the final user

Note: In the past the builds was compiled in Adoptium but now, we will have to compile in Github actions. What is your big plan to compile in Github Actions?

Of course,

The changes in this PR are only changing the repository urls from the main debain repo to the archived debian repo, since stretch and buster, since they are end of life. You can see for yourself here.

Yes I tested these changes.

The PR will only affect the users if they are building it.

I did not know this project is moving to Github Actions, and this PR won’t affect anything with that.

Thank you for your time

I need the changes tested in the PR.

I will close this PR and unify the conversation in the another PR. #80

When the complete plan and team will be defined, I will accept this and others PR related to this repository. Any change require an automatic build in a Pipeline, in this case Github Action.

Juan Antonio

@jabrena do you plan implement the Github Action Pipeline yourself?

I will review the PRs to approve and merge but I am waiting it from future PR.
It is not only to send a PR to a repository, it is necessary to build it.